fix(reporting): use timezone-aware utc datetime in exported reports - #2018
fix(reporting): use timezone-aware utc datetime in exported reports#2018NiravaM wants to merge 1 commit into
Conversation
utksh1
added
level:beginner
utksh1
left a comment
utksh1
left a comment
There was a problem hiding this comment.
Please remove the unrelated root package-lock.json; this backend timestamp fix should not add an empty frontend lockfile. Also add a focused report-payload test asserting generated_at is UTC-aware/UTC-derived, then rerun checks.
utksh1
left a comment
utksh1
left a comment
There was a problem hiding this comment.
The prior blockers remain unresolved: remove the unrelated root package-lock.json, add the focused UTC report-payload test, resolve the merge conflict, and fix backend-unit before re-review.
utksh1
left a comment
utksh1
left a comment
There was a problem hiding this comment.
The prior blockers remain unresolved: remove the unrelated root package-lock.json, add the focused UTC report-payload test, resolve the merge conflict, and fix backend-unit before re-review.
utksh1
left a comment
utksh1
left a comment
There was a problem hiding this comment.
Still blocked: remove the unrelated root package-lock.json, add focused generated_at UTC regression coverage, resolve the merge conflict, and fix backend-unit.
2 participants
Description
The
generated_attimestamp in exported reports was being populated using a naive local datetime (datetime.now()). This was inconsistent with the timezone-aware UTCdiscovered_attimestamps used elsewhere in the codebase, leading to off-by-timezone confusion in exported reports.This change updates the
generated_atfield generation in the report payload to use a timezone-aware UTC datetime (datetime.now(timezone.utc)).Related Issues
fixes #1829
Type of Change
Checklist